<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML>
<HEAD>

<meta name="copyright" content="Copyright (c) Thales Corporate Services S.A.S, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<meta name="author" content="Benoit Langlois" >
<meta name="keywords" content="activity"/>

<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">

<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<title>Activity</title>
</HEAD>
<BODY BGCOLOR="#ffffff">

<table border="0" cellpadding="2" cellspacing="0" width="100%">
  <tbody>
    <tr>
    	<td colspan="2" align="left" bgcolor="#0080c0" valign="top">
    	  <h2><font face="Arial,Helvetica"><font color="#ffffff">
    	  &nbsp;Activity
    	  </font></font></h2>
    	</td>
    </tr>
	</tbody>
</table>

<a name="definition"><h2>Definition</h2></a>
<p class="Para">An activity is a work unit with a work context. Applied to generation in EGF, an activity is a generation unit.</p>
  
  
<a name="motivation"><h2>Motivation</h2></a>
<p class="Para">An activity defines a work unit in a software process. The purpose of EGF is to target automated activities. Factory component and task are examples of activities. This list is extensible. For instance, process could be a candidate of new activity.</p>

<a name="structure"><h2>Structure</h2></a>

<p class="Para">An activity has a name, description and a set of contracts that represent the activity parameters. This basic structure is specialized afterward by activity subclasses, such as the factory component that contains viewpoints and an orchestration where activities can be called.</p>
<br/>
 

<p align="center">
<img src="./images/activityStructure.jpg" alt="Activity Structure"/>
</p>
<p align="center">
<i>Figure 1. Activity structure</i>
</p>


</body>
</html>
